A versatile memory-mapped I/O interface for microcomputers

Two virtual memory mapped network interface designs

In existing multicomputers, software overhead dominates the message-passing latency cost. Our research on the SHRIMP project at Princeton indicates that appropriate network interface support can signi cantly reduce this software overhead. We have designed two network interfaces for the SHRIMP multicomputer. Both support virtual memory mapped communication allowing user processes to communicate ...

Virtual Memory Mapped Network Interface for the SHRIMP Multicomputer

A UNIX Interface for Shared Memory and Memory Mapped Files Under Mach

This paper describes an approach to Unix shared memory and memory mapped files currently in use at CMU under the Mach Operating System. It describes the rationale for Mach’s memory sharing and file mapping primitives as well as their impact on other system components and on overall performance.

Fast RPC on the SHRIMP Virtual Memory Mapped Network Interface

The emergence of new network interface technology is enabling new approaches to the development of communications software. This paper evaluates the SHRIMP virtual memory mapped network interface by using it to build two fast implementations of remote procedure call (RPC). Our rst implementation, called vRPC, is fully compatible with the SunRPC standard. We change the RPC runtime library; the o...

Memory - Mapped Transactions

Memory-mapped transactions combine the advantages of both memory mapping and transactions to provide a programming interface for concurrently accessing data on disk without explicit I/O or locking operations. This interface enables a programmer to design a complex serial program that accesses only main memory, and with little to no modification, convert the program into correct code with multip...